What's New in 9.5.0.0

The release of OIPA 9.5.0.0 contains significant enhancements to the OIPA application. An explanation of the enhancements is provided below. Click the links within each enhancement to see the prototype samples and additional information provided in this help system.

Enhancements Included in 9.5.0.0

  • Activity Enhancements

    • A new Activity Confirmation screen is supported. The new ConfirmationScreen rule is used to configure the screen. An activity confirmation number can be generated through the use of Identifier fields and a new Identifier math variable. View prototype example

    • A new tool-tip configuration element was introduced to the TransactionCosmetics business rule in order to add some flexibility to the tool-tips functionality. The activity confirmation number associated with an activity can be displayed in the tool-tip bubble. Display of other transaction fields is also configurable.
    • The Activity Shading feature was added to the CompanyCosmetics rule. When enabled (configured with ENABLE="Yes"), this feature displays activities in the Activity screen with colored text that gives the user a visual cue to the activity status.

    • The <FieldsDoNotExist> element was added to the RolesExist rule to provide a means through configuration of verifying whether certain fields are empty at the time an activity is processed.

    • OIPA has been enhanced to include the ability to preview activity results and to verify the activity detail through a new Quote screen before an activity is processed. A new Verification screen has also been added. View prototype example

  • Address

    • When a change to an existing client address is made, OIPA can automatically spawn an activity on the Client Activity screen that will generate an Address Change letter. This will all happen automatically if configuration is in place to support this functionality. View the prototype
    • Three new transaction elements were added: <Address>, <AddressTypes> and <AddressType>. Refer to the XMLConfiguration Guide in the Help section of the Rules Palette for a complete explanation of the new elements and the attributes supporting them. This rule can be found in the Transaction Rules | Transaction Elements section of the Table of Contents.

    • A new business rule called CreateClientAddress was added with an element called <ClientGUID>. This allows one or multiple client GUIDs to be updated. Refer to the XMLConfiguration Guide in the Help section of the Rules Palette for a complete explanation of the new rule. This rule can be found in the Configuration Overview | Business Rules | Attached Rules section of the Table of Contents.

  • Allocations

    • Allocation models are now supported in OIPA. There are four types of allocation models: Non-Editable Non Asset Class Models, Non-Editable Asset Class Models, Editable Non Asset Class Models and Editable Asset Class Models. Refer to the Allocation Models section for a full explanation of Allocation Models.
    • Three new transaction elements were added: <Address>, <AddressTypes> and <AddressType>. Refer to the XMLConfiguration Guide in the Help section of the Rules Palette for a complete explanation of the new elements and the attributes supporting them. This rule can be found in the Transaction Rules | Transaction Elements section of the Table of Contents.

    • A new business rule called CreateClientAddress was added with an element called <ClientGUID>. This allows one or multiple client GUIDs to be updated. Refer to the XMLConfiguration Guide in the Help section of the Rules Palette for a complete explanation of the new rule. This rule can be found in the Configuration Overview | Business Rules | Attached Rules section of the Table of Contents.

    • A new business rule called PolicyAllocationScreen was added to drive the configuration of the OIPA Allocation screen when allocation models are used. This rule is automatically created as a Plan Rule when a new plan is created.
    • A new business rule called TransactionAllocationScreen was added to drive the configuration of the Allocation tab for activity allocations. It allows OIPA to capture the functionality for models and funds.

    • OIPA has been modified to provide the ability to display both the original and the final allocations on the Activity Results screen. View Prototype example

  • Annuitization with Overflow

    • OIPA supports functionality that guarantees periodic payments are produced from a Variable Annuity policy. These payments are guaranteed in that it is possible for the sum of all payments over the policy lifecycle to exceed the value of the deposits. The underlying allocation of these payments is made from sub accounts (funds) linked to the policy’s current investments and held on the AsBenefitSplit table. View Prototype example

  • CopyBooks

    • CopyBooks can be overridden at various levels. Rules contexts were developed to define override capability and provide a means of rule classification based on override levels.

  • Currency Enhancements

    • The <RoundCurrencyEntry> element was added to the CompanyCosmetics rule to indicate that a Money data type screen or transaction field will automatically round the entered amount to the specified significant digits of the currency (DisplayRoundPlaces ) using the CurrencyRoundMethod on the AsCurrency table. If this element is not present, then the default method is to truncate the entry. View Prototype example

    • Screen Math, Actions and Events now support Money and Currency data types. Screen math is able to perform arithmetic and comparison operations on currency values. Screen actions can compare currency values and assign new ones to the fields. View prototype example

  • Cycle

    • The CycleSequence rule was introduced to define the order in which companies and plans run through cycle. The order can be changed for specific business conditions such as month end and unplanned market closures. A new administration node called Cycle Sequence was added to the Admin Explorer tab.

  • Disbursement Enhancements

    • The Disbursement Approval screen supports dynamic fields that can be used to search for disbursement records. A new optional element was added that allows the disbursement amount column to be totaled for each page of information displayed on the screen. Refer to the XMLConfiguration Guide in the Help section of the Rules Palette for a complete list of elements and attributes supported in this business rule. This rule can be found in the Business Rules | Screen Rules section.
    • A new attached business rule, DisbursementUpdate, can be attached to a transaction to initiate a disbursement status update when the activity is processed. View prototype example

  • Error Messages with Substitutions

    • A math variable, field or system value using prefixes can be inserted into an error message to provide additional error details to the user. View prototype example

  • External Database Access for Client Information

  • Field Enhancements

    • OIPA can now store and display a larger amount of data than was previously supported in the dynamic text fields. A new TextArea data type was added as a common field data type. Multifield rules support this new data type. A new math data type BIGTEXT was also added and can receive data from a field with a data type of Text Area. View prototype example

  • Function Overrides

    • OIPA has been modified to provide the ability for user defined functions to be overridden in the same manner as CopyBooks.

  • Fund Enhancements

    • In previous versions of OIPA, funds were defined at the plan level. A Funds node was available in the Main Explorer in the Plans folder. The Funds node has been moved to the Admin Explorer in the Administration folder. Now fund information is captured at the company level and can be reused at the plan level.

    • Assignment processing was expanded to support index funds. A BUCKET and BUCKETEFFECTIVEDATE attribute were added. The ability to build buckets during valuation processing was also implemented.

  • Plans

    • The PlanOrder rule was implemented in this release. This rule allows plans to be sorted in ascending or descending order in the Plan and Plan Group drop down boxes on screens in OIPA.

  • Policy Enhancements

    • The PolicyOverviewScreen rule is now supported in the 9.5 version of OIPA. This display only screen provides the user with a snap shot view of policy detail, general segment, policy/segment role data and values information on one screen. It is the first link listed on the Left Navigation menu of the Policy screen.

    • Policy Role functionality was enhanced to provide standardization in the handling of all roles; both policy and segment. Policy role views can be configured to control the ordering of policy roles for presentation on the Role screen.

    • OIPA provides the ability to shadow (soft delete) policy records. Policy status codes that represent a shadowed status are configurable. A Shadow Policy button on the Policy screen is available to shadow a policy based on the current status of the policy. This is typically used for pending policies that were added in error. View prototype example

  • Precision Rounding Business Rules
    • The UnitValuesPrecision business rule was absorbed by the PrecisionValues business rule. The UnitValuesPrecision rule was deprecated. All functionality is fully represented in the new PrecisionValues rule

  • Programs

    • Users are now able to inquire and change indicative program data and scheduling information in a unified programs view, rather than piecing together these facts by looking at activities and activity history. View prototype example

  • Rates

    • The CreateRates rule was implemented to create a new Rate Group for an existing Rate Table and optionally close an existing Rate Group if needed.

    • Enhancements were made to the standard rate access of OIPA. Custom rate tables and retrieval routines are now supported. This customization does not extend to fixed fund interest rates as these must remain in OIPA rate table structures. System properties will indicate the type of rate retrieval functionality that OIPA executes.

  • Required Fields
    • Required fields on screens in OIPA are now visually identified on the screen. An error will occur if a required field is not populated by the user.
  • State Approvals: The Rules Palette provides a State Approval editor to record the states that have approved sale of an insurance product by plan and segment. The state approval records are assigned a starting effective date and end or expiration date. The system uses these state approval records to control whether or not a plan or segment is available in OIPA for a particular state.
  • Suspense Refund Number
    • When a suspense refund is processed in OIPA, a suspense refund number is automatically generated by the system and can be passed to multiple screens, spawned transactions, business rules, etc.

  • Transactions

    • A new transaction type, Non-Reversible/Non-Reversing, was created. These transactions cannot be reversed and recycled without using a Delete checkbox on the Activity screen. Recycling and reversing any activities prior to the transaction will NOT cause this activity to be reprocessed. View prototype example

    • Undo/Redo processing can be performed on spawned and Non-Reversible transactions if a user has the proper security privileges. A Delete checkbox was added to the Filters section of the Activity screen. If a user has the proper security privileges, clicking the Delete check box will add a delete and recycle icon next to an active spawned or non-reversible transaction.

    • A new transaction type, Reversible/Non-Reversing, was created. These transactions reverse/recycle through normal undo/redo processing and can be edited or deleted. Recycling and reversing this activity will not cause activities after it to be reprocessed.